| Add2it Go-To Enterprise - readme.txt: - Demo Mode: On |
| ########################################## # Add2it Go-To Enterprise V1.01 04/06/07 # # Download at: http://www.add2it.com # ########################################## # Copyright 2001-2007 by Frank Bauer # # Add2it.com - All Rights Reserved. # ########################################## Contents: ######### 1. Description & Features 2. Add2it Affiliate Program 3. Script Info 4. Copyright Notice 5. Disclaimer 6. Installation Instructions 7. Script History 8. Manual 9. Support Forum 10. Add2it Scripts Update + Announcement List 1. Description & Features : ########################### You can find the most current description and list of features at: 2. Add2it Affiliate Program : ############################# You can find all details about the Add2it.com Affiliate Program and how you can earn up to 50% commissions at: The Add2it.com Affiliate Program Sign-Up Form is located at: Affiliates can log-in at: 3. Script Info : ################ Version: 1.01 Take a look at the online demo at: 4. Copyright Notice : ##################### This scripts is for your use only and you may NOT distribute them to other parties. You can install this script per license ONE TIME on ONE server and it is not allowed to make modifications in any way, shape or form to the scripts. Add2it.com has spent 100's of man hours to create a software to help you - please respect OUR RIGHTS in giving you this software for your unlimited usage, by NOT violating our rights as the sole copyright owners and creators of this scripts. You may not in any way, shape or form adjust, reprogram or change this scripts. All coding is copyright Frank Bauer, Add2it.com and is licensed to you for your usage only. This scripts and all it's components are whole created, owned, and copyrighted Add2it.com. In other words you are only allowed to install and use this scripts ONLY - you may NOT change it, or use any part of it in whole or in part in any other program or any other way, shape or form without permission of Add2it.com. By installing and/or using this scripts you agree to these terms and shall be binding in a court of law - in all countries worldwide - forever. All people that violate these terms will be dealt with by legal means - any person that informs Add2it.com of a copyright violation, will be rewarded. Please visit Add2it.com if you require special services at: 5. Disclaimer : ############### This software is provided as is - Add2it.com will not be held responsible for any loss or damage indirectly or directly caused by your installing and using this scripts in any way, shape or form. By installing this scripts you agree, completely and absolutely with all terms in this README.TXT file and release Add2it.com from any and all responsibility by you using this scripts. 6. Installation Instructions : ############################## 1. To unpack the GTE101.ZIP file, go to the folder where you saved it to and unzip the file into a directory of your choice. 2. If you do not have ZIP decompression software installed on your computer, get it for free at: http://www.shareware.com3. The installation of this script is simple, no variables or setting need to be adjusted prior to upload. All settings are accessible online, via the Admin Control Center. 4. The path to Perl within the scripts is set to the typical standard value of /usr/bin/perl. This path works on 90% of the servers. If you know that the path to Perl is different on your server, please consult the "Troubleshooting" section below to see in which files the path to Perl has to be changed.5. This program must be uploaded to your server where your website files are located. 6. To upload, you will need an FTP program. Either WS-FTP or CUTE-FTP, free at: http://www.shareware.com For Macs, you will need a copy of FETCH. Upload using FRONTPAGE is NOT recommended AND will NOT WORK.7. Start up your FTP program. For this example, WS-FTP software program is used. Other programs will be similar. All you are doing is moving all files from your local computer to the server where your website files are located, and setting the permissions of install.cgi to allow the script to be treated like a program.8. Login into your website account using your FTP username and FTP password. 9. Create a new a new directory for the scripts in your CGI / CGI-BIN folder or somewhere else*. The recommended name for this new directory is "go". Set the file upload to ASCII only [ASCII mode]. CGI-BIN permissions are set by the server and no attempt should be made to change them. On some servers you will have to CREATE a CGI-BIN - to do this: MKDIR cgi-bin * NOTE: If you attempt to install this in a directory other than a CGI/CGI-BIN, even with the proper permissions set on both the FILE and DIRECTORY the files are located in it MAY NOT WORK as some web servers restrict where CGI programs can operate and run.10. On UNIX systems set permissions on this new folder. Once created, CHMOD [right click - this will be under settings in other programs, other than WS-FTP] this directory to 755**. Visually, Setting are as follows [WS-FTP]: Owner USER Other Some servers MAY require CHMOD 777 or visually, setting are as follows [WS-FTP]: Owner USER Other ** "CHMOD" means change permissions to allow this program to be treated as a program [vs a webpage] and allow it to do certain things. This is only necessary on UNIX systems. On some servers, you may have to use a program called TELNET to go and change the settings... You can also view the online manuals at: For instructions on TELNET, general uploading of files and setting permissions.11. Open this folder. 12. Select the folder/directory in your computer where you unzipped the GTP130.ZIP file. 13. Upload the following files in ASCII mode to the new folder on your server: - .htaccess (upload ONLY if .pl files can't be executed)14. On UNIX systems, set the permissions of the install.pl file. CHMOD mode it [right click over the install.pl script] and also set it to 755 as above. 15. You are now ready to let the install.pl file do the rest of the installation process. Open your browser and call install.pl to install the rest of the script. Depending on where the new directory is located the path could be e.g.: All sub-directories will be created automatically, all files will be moved into the proper sub-directories and on Unix systems all file and directory permissions will be adjusted automatically. If there is any problem, the script will let you know what it is.16. Then call install.pl to setup the script. All necessary variables will be set. Please enter the URL to the directory where the scripts are located, choose if you want all outgoing emails to be send with Sendmail (Unix) or with your SMTP server (Unix or Windows), enter the administrators email address and password. Modify all other settings as you like. 17. Now you need to enter your order number as well as your order password for this script. Please enter them to finish the registration. 18. Click on "Links & Stats" and enter the link name and URL to add your first link. 19. Now you just need to setup the cron job (Unix / Linux) or scheduled tasks (Windows) for the monthly stats function (see 8.4). ...All done! Note: You can update from the free to the pro version as well as from any earlier version to the most current version at any time without losing any of your settings, links or statistics. Just upload the pro version files as mentioned in that versions readme.txt file and leave all other files on your server as they are. Troubleshooting : ================= 1. First, if you get an error - make sure you uploaded all files in ASCII format only. Uploading in BINARY will corrupt the files. 2. If you attempt to run the script, and get a server error double check you set the permissions as shown above on both the DIRECTORY the script is uploaded to AND the FILE install.pl - if you still get an error try CHMODing the DIRECTORY ONLY to 777 [visually, all permissions are "YES"], then re-try the script initialization. If necessary, adjust the path to Perl within these files: - admin.cgi At the top of each script (and it must remain as the first line) is a default path to the Perl program on your host server. This can vary slightly between UNIX servers. If you have problems running the scripts, check with your host support staff about the correct path described in this line. The default entry is "#!/usr/bin/perl" and another common variation is "#!/usr/local/bin/perl". In Perl scripts the hash sign "#" character comments out the code on a line starting with this character. Here it has a special meaning to Perl. NOTE: If you attempt to install this in a directory other than a CGI/CGI-BIN, even with the proper permissions set on both the FILE and DIRECTORY the files are located in it MAY3. Upon initialization "I can't create this file" - This means the permissions are wrong on the DIRECTORY only - the one you created to upload the files to. Check as noted above in number 2. 4. I try to send myself a statistics report and get a server error. This means the SENDMAIL or SMTP server settings are incorrect for your script. Click on "Change the settings of Add2it Go-To Enterprise", and check the SENDMAIL or SMTP server settings. Consult with your webhosting company for the CORRECT SENDMAIL or SMTP server settings for your server.5. For all other troubling shooting and questions visit: http://www.add2it.com/cgi-bin/discus/show.cgi?742/7426. If you would like to have this script installed on your website, please order the Installation Service at: http://www.add2it.com/scripts/order.shtml 7. Script History : ################### You can find the Script History online at: 8. Manual of Add2it Go-To Enterprise : ###################################### 8.1 The administrator and the users need the index.pl script to: - User Manager (Admin only) - Add Users - Allows you to add new users - View Users - Links & Stats - View stats - Add new links - Edit links - Reset link counters - Delete links - Receive a link statistic report via email - Change the settings of Add2it Go-To Enterprise Here is an example for the header area:<html> <head> <title>Add2it Go-To Enterprise - ^title^</title> <style> <!--A:link { COLOR: #cc0000; TEXT-DECORATION: underline } A:visited { COLOR: #990000; TEXT-DECORATION: underline } A:hover { COLOR: #009900; CURSOR: hand; TEXT-DECORATION: underline } --> </style> </head> <body bgColor=#FFFF99 vLink=#990000 link="#CC0000"> <div align="center"> <center> <table border="0" width="90%" cellspacing="0" cellpadding="2"> <tr> <td width="100%" bgcolor=#003399><font face="Arial, Helvetica, sans-serif" size=2 color=#FFFF99><b>Add2it Go-To Enterprise - ^title^</b></font></td> </tr> </table> Here is an example for the footer area:<br> <table width="90%" border="2" cellpadding="2" cellspacing="0" bordercolor="#003399"> <tr> <td width="30%" align="center"><b><font face="Arial, Helvetica, sans-serif" size=1 color="#003399"> ^add2it^ </font></b></td> <td width="40%" align="center" bgcolor=#003399> ^language^ ^admin^ </td> <td width="30%" align="center"><b><font face="Arial, Helvetica, sans-serif" size=2> ^back^ </font></b></td> </tr> </table> </center> </div> </body> </html> The administrator calls the index.pl with: http://www.yourdomain.com/cgi-bin/go/index.pl?language=<language-sub-dir>&admin=1 Users call the index.pl with: http://www.yourdomain.com/cgi-bin/go/index.pl?language=<language-sub-dir> 8.2 The administrator and the users need the to.cgi / to.pl script to: - automatically fowarded ad viewers to the requested URL and to test a link without counting Ad viewers call to.pl with this links: http://www.yourdomain.com/cgi-bin/go/to.pl?l=<link name>&u=<username> (User Link) http://www.yourdomain.com/cgi-bin/go/to.pl?l=<link name>&language=<language-sub-dir> (Admin Link) http://www.yourdomain.com/cgi-bin/go/to.pl?l=<link name>&language=<language-sub-dir>&u=<username> (User Link) Administrators can call to.pl with this links (to test without counting): http://www.yourdomain.com/cgi-bin/go/to.pl?t=<link name>&language=<language-sub-dir> Users can call to.pl with this links (to test without counting): http://www.yourdomain.com/cgi-bin/go/to.pl?t=<link name>&language=<language-sub-dir>&u=<username>8.3 The users need the signup.pl script to: - Signup for an user account without admin manually adding user Users can call signup.pl with this links: http://www.yourdomain.com/cgi-bin/go/signup.pl?language=<language-sub-dir>8.4 The server needs the stats.pl script to: - Automatically update the stats and send an overview via email to the admin and the users. This script needs to be called by a cron job (Unix / Linux) or scheduled tasks (Windows). The way to setup a cron job or scheduled tasks may vary from host to host. If you are not sure about how to do this, please contact your web hosts technical support staff. With Kiosk and Host4Profit you can simply set up cron jobs in the control panel. Note: If your web hosts does not permit cron jobs or scheduled tasks, call the script on the first day of the month manually in your browser: On Unix / Linux: The cron job line to call the script once at midnight of the first day of the month will need to look like this: 0 0 1 * * /path/to/gte/stats.pl Note: If your on a Kiosk or Host4Profit server or with any other host that provides cron job setup in a control panel, you can completely ignore the following part of this chapter. For everyone else: A cron event is an automatic feature to call a script at given intervals. In the case of this script, to call the script e.g. each full hour or every 5 minutes to continue to send the scheduled messages. Out of all the setup objectives in this manual, this one is without a doubt going to be the most complicated and tricky, especially for the beginner. However, if your host will run a cron event for you, you can skip this chapter. If not, and you're a beginner, you might want to contact someone you know that's familiar with SSH, secure Telnet or running cron events. In either case, you'll need to run a cron event on a 'cron.txt' file that contains the above cron job line. First of all, you'll need to verify with your hosting service that you do indeed have SSH capabilities. You can simply contact them and request information on that. Just ask them to activate SSH for you and ask them if they'll run the cron for you. If they will run it for you, then just give them the path to the path to the 'cron.txt' file that contains the above cron job line. You'll need to have SSH to do this, unless someone does it for you in which case they'll need SSH. You can go to http://www.vandyke.com and download a free, 30 day evaluation copy of Secure CRT. This will give you the ability to run the cron. You only need to run the cron once! SecureCRT includes strong cryptography. U.S. export regulations for encryption software require an eligibility screen before downloading is allowed. This means they'll need some basic information about you before you download the program. After downloading, simply install the program and it will put an icon on your Windows desktop. After downloading SecureCRT, the first thing you need to do with it is create an "Identity File". An identity file is required for RSA authentication. Setting Up RSA Authentication: Overview of RSA Authentication: RSA authentication uses a public-private key pair to authenticate and log in to an SSH1 Server. It offers a higher level of authentication security than password authentication by requiring both the private key and the passphrase that protects the private key in order to complete authentication. Setting up RSA authentication for a SecureCRT session is a multi-step process. Identity files are created with the RSA key generation wizard. The identity file is defined for global or session-specific use in the advanced SSH options dialog. Then the public key is added to the authorized_keys file located on the SSH server (your hosting service). Note: Only SSH1 supports RSA authentication. Creating Identity Files: To create an RSA identity file: a) In the connect dialog, select the SSH1 session with which you would like to use the identity files. b) Open the session options dialog and in the connection category, click the advanced button. c) Select the general tab and click on the create identity file button in the identity filename section. d) Follow the instructions in the RSA key generation wizard to create your identity files. Once your public-private key pair has been generated by the RSA key generation wizard, you will be prompted for the path and filename in which your private key will be stored. Be sure to specify a secure location for this file such that you are the only individual with access to it. The public key will be placed in a file with the same basename as the private key file, but with an extension of .pub. Using Your Identity Files: Once you have created your identity files, there are several steps that will need to be completed so that you can make use of them with SecureCRT. The necessary steps are: 1) Transfer the identity.pub file to the remote machine 1. Transfer the Identity File to the SSH1 Server In order to use your public key you must transfer the xxxxxxxx.pub file created by the key generation wizard to the ~/.ssh/ directory on the SSH1 server. One of the easiest ways to transfer this file to the SSH1 server is to use the ZModem file transfer feature provided by SecureCRT. If the remote machine does not have ZModem installed, you will need to use an FTP client to transfer the identity file to the remote machine. Another way to transfer the identity file to the remote machine is to copy and paste the contents of the identity file. This is how it works with Host4Profit. To accomplish this, use Notepad.exe to open the identity file and copy the contents of the identity file to the clipboard. On the remote machine, create a file using your favorite editor and paste the contents of the clipboard using the paste button. 2. Update the authorized_keys File on the Remote Machine Once you have transferred the identity.pub file to the remote machine, you must update the authorized_keys file on the remote machine. The following steps outline this update process. a) Connect to the remote SSH1 server using SSH1 and password authentication. b) Append the contents of the public key file created with the RSA key generation wizard to the file ~/.ssh/authorized_keys on the remote host. The default name of the public key file is identity.pub. Create the ~/.ssh/authorized_keys file if it does not already exist. If you want multiple authorized keys, append the contents of the public key file to the authorized_keys file. The simplest way to do this is typically: % cat identity.pub >> ~/.ssh/authorized_keys (note that the name of the identity file can be different than the example) Note on placing public keys: The format of the authorized_keys file requires that each entry consist of a single long line. If you use copy and paste to add a public key to the ~/.ssh/authorized_keys file, make sure that the entry contains no additional newline characters. 3. Configure SecureCRT to use your Identity Files The identity file created by the key generation wizard contains both your new public key and your new private key. To configure SecureCRT to use the identity file: a) In the Connect dialog, select the SSH1 session with which you would like to use the identity file. b) Open the Session Options dialog and in the Connection category, change the Authentication setting from Password to RSA. c) If you have more than one identity file, you may need to click on the advanced button and verify that the session is using the session-specific key you have created. d) Click on the OK button to save the changes. If you supplied a passphrase when you created your key, you will be prompted to enter it during the connection process. In closing, this can be tricky for most people, so you might want to contact a support professional to do this for you if you have any doubts. Just refer them to this text. If this process doesn't seem familiar to you and you're not confident by now about this process, I would recommend having someone help you through at least this phase of the install. You might also see if your web hosts technical support staff will walk you through the installation. If you would like to know more about cron jobs, I can recommend this page: On Windows: If you have direct access to a Windows NT/2000/XP/2003 server machine you can use "Scheduled Tasks" from the Control Panel, pointing to the location of the "stats.bat" batch script file. It is recommended to redirect its output to a log file. For example, use C:\path_to_your_home\gte\stats.bat > gte_cronjob.log as entry in the Start Task box. This creates a "gte_cronjob.log" file which always holds the output of the last batch process. The schedule.bat would then call: C:\Perl\bin\perl.exe /path/to/gte/stats.pl 9. Support Forum : ##################
10. Add2it Scripts Update + Announcement List : ############################################### You can subscribe to the Add2it Scripts Update + Announcement List at: ########################################## # Add2it Go-To Enterprise V1.01 04/06/07 # # Download at: http://www.add2it.com # ########################################## # Copyright 2001-2007 by Frank Bauer # # Add2it.com - All Rights Reserved. # ########################################## |
|
Powered by: Add2it Go-To Enterprise 1.02 [ Read Manual | Affiliate Program | Sign-Up | Login ] © 2001-2024 by Frank Bauer / add2it.com |
Click here to go back! |